Input Sensitive Information Management
By registering regular expressions, it controls the text input by users in the business system (app/URL input field) to protect sensitive information.
Regular Expression Registration
1. Start of Regular Expression Registration
- Click on the "Sensitive Information Management" submenu under the business system.
- Click the [+Register Regular Expression] button.
- The "Register Regular Expression" slide panel opens on the right.
2. Basic Information on Regular Expressions
Name (required)
- Enter a name that can identify the regular expression
- Example: "Resident Registration Number", "Credit Card Number", "Mobile Phone Number" etc.
Description (optional)
- Detailed explanation of the corresponding regular expression will be entered.
- Specifies what types of sensitive information are detected.
3. Regular Expression Pattern Input (Required)
Writing Regular Expressions
- Enter the pattern of the sensitive information you want to detect using regular expressions.
4. Regular Expression Test
Test text input
- Enter sample data in the "Regular Expression Test" input field.
- You can check in real-time whether the entered regular expression matches correctly.
Check Matching Results
- When matching with the regular expression: display success message
- When the regular expression does not match: Display the error message "The entered regular expression does not match."
- A complete pattern must match to be recognized as correct.
5. Save Regular Expression
- After entering all the information and completing the test, click the [Register] button.
- Clicking the [Cancel] button will close the panel without saving the entered content.
Standard Regular Expression Examples (Reference)
Frequently used standard regular expressions for sensitive information detection. Written in common regex engine syntax (PCRE/JS/Java/.NET), and structured to ensure that false positives (broad detection) are safer than false negatives due to DLP characteristics.**Each pattern should be validated by entering a sample using the "Regular Expression Test" function above before registration.**Hello.
*Note: Currently\bis not available due to issues in functionality implementation. Explicitly\bto(?<![A-Za-z0-9_])...(?![A-Za-z0-9_])You can use it.
| Division | Sensitive Information | Regular Expression | Matching Example | Note |
|---|---|---|---|---|
| Personal Identification | Resident Registration Number | \d{6}[-\s]?[1-4]\d{6} | 900101-1234567 | Gender position 1~4. Including foreigners.[1-8]. Date validation precision type is referenced below |
| Personal Identification | Foreign Registration Number | \d{6}[-\s]?[5-8]\d{6} | 900101-5234567 | Constellation 5~8 |
| Personal Identification | Passport Number (Korea) | (?<![A-Za-z0-9_])[A-Z]\d{8}(?![A-Za-z0-9_]) | M12345678 | 1 letter + 8 digits |
| Personal Identification | Driver's License Number | \d{2}-?\d{2}-?\d{6}-?\d{2} | 11-22-123456-78 | 12 digits. Adjustments based on environmental variations in regional and issuance format. |
| Communication | mobile phone number | 01[016789][-\s]?\d{3,4}[-\s]?\d{4} | 010-1234-5678 | 010/011/016~019 |
| Communication | Landline/Main Phone | 0\d{1,2}[-\s]?\d{3,4}[-\s]?\d{4} | 02-1234-5678 | Including area code. Mobile phone and matching duplicates possible. |
| Account | email address | [A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,} | user@example.com | Practical Standard Type (Not Entire RFC5322) |
| Finance | Credit Card (16 digits) | \d{4}[-\s]?\d{4}[-\s]?\d{4}[-\s]?\d{4} | 1234-5678-9012-3456 | Luhn validation is not possible with regular expressions. Refer to the patterns by brand below. |
| Organization | Business Registration Number | \d{3}-?\d{2}-?\d{5} | 123-45-67890 | 3-2-5, 10 digits |
| Organization | Corporate Registration Number | \d{6}-?\d{7} | 110111-1234567 | 6-7, 13 digits |
| Network | IPv4 Address | (?<![A-Za-z0-9_])(\d{1,3}\.){3}\d{1,3}(?![A-Za-z0-9_]) | 192.168.0.1 | Loose matching. Octet 0~255 strict type is referenced below. |
| Network | MAC address | ([0-9A-Fa-f]{2}[:-]){5}[0-9A-Fa-f]{2} | 00:1A:2B:3C:4D:5E | Colon/Hyphen Separator |
Precision·Expansion Pattern (Select)
pipe(|) is a precise pattern that is difficult to include in a table. Use it instead of the basic form above if necessary.
# Resident Registration Number — Month (01~12)·Day (01~31) Range Validation
\d{2}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])[-\s]?[1-4]\d{6}
# IPv4 — Each Octet 0~255 Strict
(?<![A-Za-z0-9_])((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.){3}(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(?![A-Za-z0-9_])
# Credit Card — By Brand (Based on IIN)
Visa 4\d{12}(\d{3})?
Mastercard 5[1-5]\d{14}
American Express 3[47]\d{13}
The above pattern is a widely used standard type but may need adjustments depending on the introduction environment and policy objectives. Items with significant format variations, such as driver's license, landline phone, and account number, particularly require environmental verification. Be sure to validate through the testing function within the product before registration.
Managing Regular Expression List
Each regular expression is managed with a unique name, and can be selected and used from this list when configuring policies later.
Setting Input Sensitive Information Policy
After registering the regular expression, you can set the following detailed conditions through separate policy settings:
1. Policy Basic Information
- Policy Name: A name that can identify the policy
- Members: Target members to whom the policy will apply
- Explanation: Detailed description of the policy
2. Select Target System
- All business systems: Apply policies to all registered business systems
- specific business system: Directly enter the URL to apply only to a specific system
3. Regular Expression Selection
- Select a pattern to apply from the pre-registered list of regular expressions.
- You can select and use multiple regular expressions.
4. Setting Conditions
- Location Conditions: Apply policy only at specific locations
- Time Condition: Apply policy only during specific time zones
- Device Conditions: Apply policy only on specific device types
5. Audit Policy
- Log Record Options: Log only blocked or log both allow and block
- Log Detail: Whether to include user input text content
6. Policy Activation
- Settings: Policy Activation/Deactivation Status
- Expiration Date: Policy Application Period Setting
Policy List Management
Check Policy List
The registered policies are displayed in a list.
Setting Policy Priorities
- You can change the order of policies by dragging and dropping them in the policy list.
- The higher the order, the higher the priority.
- When multiple policies can be applied simultaneously, the policies with higher priority are processed first.
Policy Modification and Deletion
- You can select a registered policy to modify or delete.
- When modifying the policy, the same settings screen will appear.
Log Records
- All detection and blocking events are logged according to the configured audit policy.
- When text matching the regular expression is detected, it is immediately masked and logged.
- The log includes time, user, applied policy, detected content, etc.